chore(persona-kit): refresh Relayfile trigger catalog#243
Conversation
|
Warning Review limit reached
More reviews will be available in 37 minutes and 6 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request upgrades the @relayfile/adapter-core dependency to version ^0.3.59 in both packages/persona-kit and packages/runtime. It also adds a test case in packages/persona-kit/src/triggers.test.ts to ensure lintTriggers accepts Neon sync-delta trigger events. No review comments were provided, so there is no additional feedback.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
Correction / scope clarification: this PR is not required to unblock the Neon deploy. Published So this PR should be treated as optional hardening only: it raises the minimum declared adapter-core range and adds regression coverage that Neon sync-delta triggers lint clean locally. It should not be considered a release gate for the Neon deploy. |
1 participant
Summary
@relayfile/adapter-coreto^0.3.59in@agentworkforce/persona-kitand@agentworkforce/runtimepnpm-lock.yamlso local deploy tooling resolves the catalog that includes Neon sync-delta triggersWhy
The Neon pipeline is registered server-side, but local
agentworkforce deploystill warnstriggers.neon: provider not in known-trigger registrybecause persona-kit/runtime were pinned to adapter-core versions that predate Neon. This makes the local lint path catch up to the published adapter catalog.Validation
pnpm --filter @agentworkforce/persona-kit testpnpm --filter @agentworkforce/deploy testpnpm --filter @agentworkforce/runtime test